Techniques to share application data through a messaging system

ABSTRACT

Techniques to share application data through a messaging system are described. In one embodiment, an apparatus may comprise a messaging component operative to receive a message package from a messaging service at a messaging client on a client device, the message package addressed from a source messaging account and addressed to a recipient messaging account, the recipient messaging account associated with the messaging client on the client device; extract an application data payload from the message package; receive an application service recommendation package from the messaging service, the application service recommendation package comprising an application service identifier; and an application interoperation component operative to transmit at least a portion of the application data payload to a recommended application service by the messaging client, the recommended application service identified by the application service identifier. Other embodiments are described and claimed.

RELATED APPLICATIONS

This application is a continuation of, claims the benefit of andpriority to, previously filed U.S. application Ser. No. 14/844,231,filed Sep. 3, 2015, titled “Techniques to Share Application Data Througha Messaging System,” which is hereby incorporated by reference in itsentirety.

This application is related to U.S. patent application Ser. No.14/667,576, titled “Techniques to Share and Remix Media Through aMessaging System,” filed on Mar. 24, 2015, which is hereby incorporatedby reference in its entirety.

BACKGROUND

Users may interact with each other in a messaging system, sendingmessages back and forth to each other in a text-based conversationbetween two or more users. A user may have a user account associatedwith them in the messaging system, the user account providing an onlineidentity for the user, a destination for messages directed to the user,and generally coordinating the user's access to and use of the messagingsystem. A user may access the messaging system from a variety ofendpoints, including mobile devices (e.g., cellphones), desktopcomputers, web browsers, specialized messaging applications, etc.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some novel embodiments described herein. This summaryis not an extensive overview, and it is not intended to identifykey/critical elements or to delineate the scope thereof. Some conceptsare presented in a simplified form as a prelude to the more detaileddescription that is presented later.

Various embodiments are generally directed to techniques to shareapplication data through a messaging system. Some embodiments areparticularly directed to techniques to share application data through amessaging system to empower context-appropriate configuration ofapplication services. In one embodiment, for example, an apparatus maycomprise a messaging component operative to receive a message packagefrom a messaging service at a messaging client on a client device, themessage package addressed from a source messaging account and addressedto a recipient messaging account, the recipient messaging accountassociated with the messaging client on the client device; extract anapplication data payload from the message package; receive anapplication service recommendation package from the messaging service,the application service recommendation package comprising an applicationservice identifier; and an application interoperation componentoperative to transmit at least a portion of the application data payloadto a recommended application service by the messaging client, therecommended application service identified by the application serviceidentifier. Other embodiments are described and claimed.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of the various ways in which the principles disclosed hereincan be practiced and all aspects and equivalents thereof are intended tobe within the scope of the claimed subject matter. Other advantages andnovel features will become apparent from the following detaileddescription when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of an application data messagingsystem.

FIG. 2A illustrates an embodiment of a user interface displaying anapplication interface.

FIG. 2B illustrates an embodiment of a user interface displaying amessaging conversation with an application messaging item.

FIG. 2C illustrates an embodiment of a user interface displaying anapplication interface incorporating shared application data.

FIG. 3 illustrates an embodiment of a messaging client processing anextracted application data item from an application data payload.

FIG. 4 illustrates an embodiment of an additional application data itembeing added to an application data payload to generate an updatedapplication data payload.

FIG. 5 illustrates an embodiment of a logic flow for the system of FIG.1.

FIG. 6 illustrates an embodiment of a centralized system for the systemof FIG. 1.

FIG. 7 illustrates an embodiment of a distributed system for the systemof FIG. 1.

FIG. 8 illustrates an embodiment of a computing architecture.

FIG. 9 illustrates an embodiment of a communications architecture.

FIG. 10 illustrates an embodiment of a radio device architecture.

DETAILED DESCRIPTION

Users may message with each other through a messaging system. Theirconversations may include the discussion of media, entertainment,events, travel, future plans, and other elements of their lives. In somecases, the users may use application services—which may incorporate oneor both of application software executing locally on the same devicewith which they are messaging and online services accessible from thesame device with which they are messaging—to discover, retrieve, store,reserve, configure, or otherwise carry out actions related to suchelements. These users may benefit from interoperation between amessaging client and the application services that provide functionalityso as to empower them to share the functionality of the applicationservices through the messaging client.

Of particular use may be context information related to elements sharedusing a messaging system. A media item may be associated with keywordsdescribing its content. A reservation item may be associated withlocation information and time information describing where and when thereservation is for. A game item may be associated with state informationdescribing the state of a multiplayer game. In general, applicationservices may generate both a display-oriented item designed for displayto and comprehension by a human user and context data for thedisplay-oriented item expressing information related to thedisplay-oriented item for use by the application service with referenceto another user or by another application service altogether.

For example, media items may be shared with keywords, such that a userreceiving a media item via a messaging service (e.g., image item,animated image item, video item, audio item) may be displayed the mediaitem in a messaging client while the keywords for the media item arereceived and cached by the messaging client to aid media applicationservices in perform media tasks related to the media item using thekeywords. For example, a messaging client for a user account may receivefrom another user account a message containing an animated image of acorgi being vacuumed. The media item may be received in a messagepackage along with an application data payload containing a listing ofkeywords, such as “corgi” and “vacuum.” The receiving user might thenselect a media application service to look for their own image to share,either the same media application service as responsible for the imagetheir received or a different one. This selected media applicationservice may be sent the keywords so as to offer the user the opportunityto find related images.

Similar examples exist for other types of shared application data. Adinner reservation at a restaurant might be displayed in an attractiveformat that encapsulates the shared reservation for a human reader,while also being transmitted with context information for thereservation, such as a location (e.g., a street address) for therestaurant and a precise indication of a time for the reservation. Thistime and location information might be passed to a transportationapplication service to arrange for transportation to the specifiedlocation by the specified time. This transportation reservation mightthen also be shared via the messaging service, adding its applicationdata to the shared application data payload and thereby allowing foradditional interactions branching off from the sharing of thetransportation reservation. A similar process may be performed inrelation to airplane reservations, hotel reservations, or other shareditems that have a relation to a time and a place. More broadly, similarprocesses may be performed in relation to any shared items so as toleverage context about those shared items in various applicationservices.

As such, users may benefit from sharing information via a messagingsystem with the shared information comprising both human-readableelements and machine-readable elements, with the human-readable elementsdisplayed for users of the messaging system and the machine-readableelements cached for use in configuring application services. As aresult, the embodiments can improve the functioning of both a messagingsystem and application services accessible to the messaging system,improving the extendibility, interoperability, and modularity of onlineinteractions.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. It maybe evident, however, that the novel embodiments can be practiced withoutthese specific details. In other instances, well known structures anddevices are shown in block diagram form in order to facilitate adescription thereof. The intention is to cover all modifications,equivalents, and alternatives consistent with the claimed subjectmatter.

It is worthy to note that “a” and “b” and “c” and similar designators asused herein are intended to be variables representing any positiveinteger. Thus, for example, if an implementation sets a value for a=5,then a complete set of components 122 illustrated as components 122-1through 122-a may include components 122-1, 122-2, 122-3, 122-4 and122-5. The embodiments are not limited in this context.

FIG. 1 illustrates a block diagram for an application data messagingsystem 100. In one embodiment, the application data messaging system 100may comprise a computer-implemented system having software applicationscomprising one or more components. Although the application datamessaging system 100 shown in FIG. 1 has a limited number of elements ina certain topology, it may be appreciated that the application datamessaging system 100 may include more or less elements in alternatetopologies as desired for a given implementation.

A user's access to an application data messaging system 100 may be amessaging client 140 installed as a user application on a client device,such as on sender client device 190 or recipient client device 120, andexecuting locally on the client device. In some cases, the messagingclient 140 may include other functionality. For example, the messagingclient 140 may be a front-end to a social-networking service, providingmessaging services in association with the social-networking service. Inmany cases, this client device may be a smartphone, cell phone, or othermobile device using a mix of Wi-Fi and cellular data networks to accessthe Internet and networked resources, though it will be appreciated thatany form of network access may be used. For example, one device maytether to another, such as a smart watch tethering to a Internet-capabledevice (e.g., mobile phone, personal computer) or a mobile phonetethering to a personal computer. The client device may execute aplurality of applications, including the messaging client 140, one ormore applications 130, and other user applications. In otherembodiments, however, the client device may comprise a personal computerdevice, a portable digital assistant, a tablet device, or any other formof computing device. Similarly, in some situations and embodiments, auser may access the application data messaging system 100 via a webportal, with the messaging client 140 executing as a web-basedapplication.

The client device may communicate with other devices using wirelesstransmissions to exchange network traffic. Exchanging network traffic,such as may be included in the exchange of messaging transactions, maycomprise transmitting and receiving network traffic via a networkinterface controller 125 (NIC). A NIC comprises a hardware componentconnecting a computer device, such as client device, to a computernetwork. The NIC may be associated with a software network interfaceempowering software applications to access and use the NIC. Networktraffic may be received over the computer network as signals transmittedover data links. The network traffic may be received by capturing thesesignals and interpreting them. The NIC may receive network traffic overthe computer network and transfer the network traffic to memory storageaccessible to software applications using a network interfaceapplication programming interface (API). The network interfacecontroller 135 may be used for the network activities of the embodimentsdescribed herein, including the interoperation of the applications 130,application servers 135, messaging client 140, and messaging server 180through network communication. For example, the messaging client 140transmitting a message package 170 to a messaging server 180 may beinterpreted as using the network interface controller 125 for networkaccess to a communications network for the transmission of the messagepackage 170.

The applications 130 may comprise locally-executing applicationsproviding service functionality to a user of the client device. Theapplications 130 may comprise local front-ends for application services,such as may be provided in conjunction with the application servers 135.The applications 130 may comprise applications operative to interoperatewith the messaging client 140.

In some cases, one or more of the applications 130 may comprise mediaapplications for one or more of searching media content, discoveringmedia content, sharing media content, storing media content, accessingmedia content, modifying media content, and combining media content.Each of the media applications may be associated one or more mediaservices, either a dedicated media application for a particular mediaservice or a media application interoperating with a plurality of mediaservices. Each of the media services may provide one or more mediaservers, such as one or more of the application servers 135, forstoring, retrieving, and generally exchanging media content. Mediaservers may distribute media repositories to local media applicationscomprising bundles of media packages, wherein each of the media packagescomprises a media element (a particular instance of media content) andassociated information. The associated information for a media elementin a media package may include an attribution record, the attributionrecord encapsulating information about the media service, mediaapplication, and other sources of the media element.

Content received from an application may include an inter-applicationlink, the inter-application link identifying content within the contentspace of the related application and/or application service and therebyserving as a deep link to the content within the application and/orapplication service. The inter-application link may empower anapplication or application server to navigate to a particular page,view, or other repository of information for the associated content. Theinter-application link may be universal across client devices withregards to a particular media application/media service. Theinter-application link may therefore allow a user to share anapplication item with sufficient contextual information to empower thereceiving user to access the application item within its context of itsassociated application/application service. In various cases, anapplication item may comprise a media item, a reservation item, an eventitem, or any other item related to the operation of an applicationand/or application service.

The messaging client 140 may comprise an application interoperationcomponent 160. The application interoperation component 160 may begenerally arranged to manage application data items and data used forthe interoperation with applications and application services within thecontext of the messaging client 140. The application interoperationcomponent 160 may operate as a crossroads for data from the plurality ofapplications 130. The application interoperation component 160 mayempower the messaging client 140 to interoperate with the plurality ofapplications 130, such as by receiving application data from theapplications 130, submitting application data to the applications 130,invoking the viewing of existing application data within theapplications 130, and moving application data from one of theapplications 130 to another.

The messaging application 130 may comprise a messaging component 150.The messaging component 150 may be generally arranged to providemessaging services to a user of the client device. Messaging servicesmay comprise the reception of messages, the sending of messages, themaintenance of a history of messages exchanged, and othermessaging-related activities. User of the messaging client 140 may beempowered to engage in messaging conversations with a plurality of otherusers in both private user-to-user conversations, in private groupconversations between three or more users, and in public conversationsgenerally open to the messaging community. The messaging component 150may interoperate with the application interoperation component 160 toenrich any of these messaging conversations with the application datamanagement by the application interoperation component 160.

The application data messaging system 100 may include a messaging server180 from among a plurality of messaging servers. The messaging server180 may operate as an intermediary between the messaging endpoints ofusers of the application data messaging system 100. The messaging server180 may track the current network address of a user's active messagingendpoint or endpoints, such as they change network (e.g., a mobileclient device moving between Wi-Fi networks, between cellular datanetworks, and between Wi-Fi and cellular data networks). The messagingserver 180 may queue messages for messaging endpoints when they areoffline or otherwise not accepting new messages. The messaging server180 may provide an ordering on messages for a particular user so as toprovide consistency in the flow of communication between the potentiallymultiple messaging endpoints that a user might use. The messaging server180 may store a messaging history for each user so as to provide accessto previously-sent or received messages for a user. The messaginghistory may include media exchanged between users using the applicationdata messaging system 100.

The messaging component 150 may transmit and receive message packageswith a messaging server 180 for delivery from or to one or more otherusers of the application data messaging system 100. A message package170 may comprise delivery information, such as one or more delivery useridentifiers identifying one or more users for the message package 170.The messaging server 180 may receive the message package 170 from asender client device 190 and deliver it to a messaging endpoint—such asan installation of the messaging client 140 on the recipient clientdevice 190—associated with a delivery user account identified by adelivery user identifier for the message package 170.

Messages transmitted via the messaging server 180 may include one ormore media elements. Where a media element for transmission is alreadystored on the messaging server 180 or on a media server accessible tothe application data messaging system 100 the messaging server 180 mayrefrain from transmitting the media element to the recipient clientdevice 120. The messaging client 140 may generate or retrieve a hash ofa media element and transmit the hash to the messaging server 180 todetermine whether a media element is already available in theapplication data messaging system 100. The messaging server 180 mayindicate whether a media element is already available and thereforeshould not be re-uploaded. The messaging server 180 may request anupload of a media element from the client device when a media element isnot determined to be available based on the hash. Similarly, where amedia element is represented as a uniform resource locator (URL) to anetwork-accessible source, the uploading of a media element may beavoided. These techniques may serve to reduce the bandwidth used insharing media elements. By using the unified platform of the mediamessaging system 110, the bandwidth usage of sharing media elements maybe reduced as the media messaging system 110 has visibility into thenetwork locations of network-accessible media elements and may storemedia elements from a plurality of media application sources usinghashing to eliminate duplicate uploads. This reduction of bandwidthusage may increase the speed of media sharing, reduce the usage of auser's bandwidth allocation from a cellular provider, and eliminate thebattery usage that may be involved in performing the upload of aapplication item, thereby reducing the overall battery usage for mediasharing.

A application item may be managed and manipulated by the applicationdata messaging system 100 according to a variety of techniques invarious embodiments. In some cases, a media element may be directlystored as computer data representation within the media package 105. Forexample, an image media element may be stored as a Joint PhotographicExpert Group (JPEG) digital image file within the media package 105. Inother cases, a media element may be stored as a reference within themedia package 105, the reference comprising a resource locator—such as aURL—providing a network-accessible address for a media element. As such,while the recipient client device 120 may cache an instance of a mediaelement on the client device for local access, a media element may beshared using the resource locator so as to avoid the client deviceuploading a media element during transmission to the second clientdevice 190. Instead, the messaging client 140 on the second clientdevice 190 may receive a media element as the resource locator and fetchan instance of a media element after reception resource locator. Thiseliminates the use of upload bandwidth for the client device withoutpotentially leverage the storage and bandwidth of the applicationservers 135 for a second client device to download a media element.Alternatively, the messaging server 180 may cache or retrieve a mediaelement and include it with the message package 170 when delivering themessage package 170 to the second client device. It will be appreciatedthat, in general, any known technique for formatting and storing mediacontent may be used. In some cases, the application data messagingsystem 100 may re-size, re-code, change the format, or change thequality level of a application item prior to uploading or prior totransmission to a destination second client device. This may beperformed to reduce the storage space used in storing a application itemor the bandwidth used in uploading or downloading a media element.

The application data messaging system 100 may use knowledge generatedfrom interactions in between users. The application data messagingsystem 100 may comprise a component of a social-networking service andmay use knowledge generated from the broader interactions of thesocial-networking service. As such, to protect the privacy of the usersof the application data messaging system 100 and the largersocial-networking service, application data messaging system 100 mayinclude an authorization server (or other suitable component(s)) thatallows users to opt in to or opt out of having their actions logged bythe application data messaging system 100 or shared with other systems(e.g., third-party systems), for example, by setting appropriate privacysettings. A privacy setting of a user may determine what informationassociated with the user may be logged, how information associated withthe user may be logged, when information associated with the user may belogged, who may log information associated with the user, whominformation associated with the user may be shared with, and for whatpurposes information associated with the user may be logged or shared.Authorization servers or other authorization components may be used toenforce one or more privacy settings of the users of the applicationdata messaging system 100 and other elements of a social-networkingservice through blocking, data hashing, anonymization, or other suitabletechniques as appropriate. For example, while interactions between usersof a social-networking service and the social-networking service may beused to learn media content preferences and the relationship betweenpreferences for different pieces of media content, these interactionsmay be anonymized prior to or as part of the learning process.

FIG. 2A illustrates an embodiment of a user interface 200 displaying anapplication interface 205. The user interface 200 may comprise a userinterface of the sender client device 190 being used to perform a taskwith an application service that will then be shared using theapplication data messaging system 100.

The application interface 205 may correspond to a portion of a userinterface for a restaurant reservation application. A restaurantreservation application may provide access to a reservation applicationservice in which reservations may be made with a reservation serversystem. The application interface 205, indicating a reservation that hasbeen made, may be reached through the use of the restaurant reservationapplication to select a restaurant, number of people for whom thereservation is to be made, and a time (e.g., data and time of day) forthe reservation.

The application interface 205 may include controls for the operation ofthe reservation application by the user of the sender client device 190.A change control may empower the user of the reservation application tochange the details of their reservation. A cancel control may empowerthe user to cancel their reservations. Other controls may be provided invarious embodiments.

An application interface 205 may include a application share control 210empowering a user of an application to share an application item, suchas the restaurant reservation depicted in FIG. 2A. The illustratedexample application share control 210 is amessaging-application-specific application share control specificallyassociated with a particular messaging application, such as themessaging client 140. Selecting the application share control 210 maytherefore directly launch (e.g., bring to the foreground) the messagingclient 140 and transfer the application item to the messaging client140.

In other embodiments, a general application share control—anon-application-specific application share control—may be used in theapplication. Selecting this general application share control mayinitiate an interface offering multiple ways to share the applicationitem, such as email, the Multimedia Message Service (MMS) extension ofthe Short Message Service (SMS) system, messaging applications includingthe messaging client 140 associated with the application data messagingsystem 100, and other methods sharing.

In some cases, a application showing a messaging-application-specificapplication share control 210 specifically associated with a particularmessaging client 140 may correspond to a messaging-application specificversion of the application. For example, the TABLE GRABBR applicationmay release a version of the TABLE GRABBR application specificallydesigned for integration with the messaging client 140 for theapplication data messaging system 100. While the messaging client 140may be operative to accept content from bothmessaging-application-specific applications andnon-messaging-application-specific applications,messaging-application-specific applications may be preferred by themessaging client 140.

FIG. 2B illustrates an embodiment of a user interface 225 displaying amessaging conversation 230 with an application messaging item 235.

In the illustrated embodiment of FIG. 2B, the messaging client 140 isdisplaying a messaging conversation 230. The illustrated messagingconversation 230 corresponds to a private messaging conversation betweentwo users. Each user is visually represented in the messagingconversation 230 by a user avatar associated with their user account forthe messaging system.

The illustrated messaging conversation 230 includes a user messageindicating that a reservation was set up for that night. Theuser-created text message is accompanied by an application messagingitem 235 comprising a human-readable portion of an application data itemreceived from the reservation application of FIG. 2A.

In some embodiments, the application messaging item 235 may be displayedin association with an attribution display element, the attributiondisplay element visually communicating the particular application fromwhich the application messaging item 235 was shared. The attributiondisplay element may further comprise a control for accessing theapplication messaging item 235 within the attributed application withwhich the application messaging item 235 is associated.

The user interface 225 includes application selection controls 240. Insome cases, application selection controls 240 may be displayed inresponse to user selection of the application messaging item 235 toprovide options for handling the application messaging item 235. Inother cases, an application launch control may be displayed as part ofthe messaging interface, with selection of the application launchcontrol providing options for dealing with any portion of theapplication data payload. Where the application selection controls 240are displayed in response to a user selection of an applicationmessaging item 235, the suggested applications may be selected accordingto a portion of the application data payload corresponding to theapplication messaging item 235, as in associated machine-oriented dataattached in relation to the human-readable application messaging item235.

In the illustrated embodiment, the application selection controls 240comprise a transport section, lodging section, and history section, thetransport section and lodging section comprising selected in response tothe application messaging item 235 being associated with an applicationdata item in the application data payload containing time and placeinformation, in this case time and place information for a restaurantreservation. An application may be indicated in the display via text,image, icons, or any other display technique.

The user of the messaging application 140 may select one of theapplication selection controls 240 to initiate the launching of anapplication. For example, the “DRIVR” icon may be selected to launch the“DRIVR” application on the recipient client device 120. In someembodiments, only applications available on the recipient client device120 may be displayed. In other embodiments, additional suggestedapplications may be displayed, with the messaging client initiating theinstallation of an additional suggested application if selected by theuser.

FIG. 2C illustrates an embodiment of a user interface 250 displaying anapplication interface 255 incorporating shared application data.

User interface 250 may comprise an application interface 255corresponding to a transportation application. The transportationapplication may have received an application data payload and/orapplication data item, the application data item indicating an addressand a time. The transportation application may use the date and time toconfigure a transportation service for the user of the recipient device190, in this case transportation to a reservation. The displayedapplication interface 255 may correspond to the user of the recipientdevice 190 having configured various options for the transportation,such as confirming a pick-up location—as may be determined as a currentlocation of the user—and pick-up time. In the illustrated example ofFIG. 2C, the application interface 255 includes a display of the pick-uplocation, drop-off location, and a map of the route to be taken betweenthe pick-up location and drop-off location.

The user may be aided in the configuration of the transportation throughthe transportation application receiving the destination address, thedestination address added to the application data payload by themessaging client 140 on the sender client device 120 as received from areservation application. The transportation application may receive thedestination address and automatically configure the destination addressfor a trip based on the received destination address. In some cases,such as where an immediate trip is being requested, the time of thereservation may not be used by the transportation application, withinstead only the destination address being used from a receivedapplication data item.

The application interface 255 may also include an application sharecontrol 260 substantially similar to the application share control 210described with reference to FIG. 2A. The application share control 260may be used to share the configured transportation in a messagingconversation, such as may be beneficial where the transportation serviceitself is to be shared with the partner in the messaging conversation.

FIG. 3 illustrates an embodiment of a messaging client 140 processing anextracted application data item 355 from an application data payload350.

A messaging component 150 may be generally arranged to receive a messagepackage 170 from a messaging service 180. A message package 170 may beaddressed from a source messaging account and addressed to a recipientmessaging account. The recipient messaging account may be associatedwith the messaging client 140 on the recipient client device 120. Themessaging component 140 being arranged to receive the messaging packagemay comprise the message component 150 receiving an incoming networkcommunication from the messaging server 180 and delineating the contentsof the incoming network communication according to a predefinedcommunication scheme.

The messaging component 150 may extract an application data payload fromthe message package 170, the application data payload comprising one ormore application data items. The messaging component 150 extracting anapplication data payload from the message package 170 may correspond tothe messaging component 150 processing a particular field or fields ofthe message package 170. The application data payload 350 may comprise,without limitation, at least one of time information, locationinformation, event information, and reservation information. Theapplication data payload 350 may comprise a pointer to a playlist formedia content to empower the shared playing of a playlist. Theapplication data payload 350 may comprise a cursor or time indicator fora current position in the playback of media content to empower thesynchronized viewing and/or listening to media content. The applicationdata payload 350 may comprise a pointer to an online game and/or gamestate information for a game.

The messaging component 150 may also receive an application servicerecommendation package from the messaging service 180, the applicationservice recommendation package comprising an application serviceidentifier. The application service identifier may indicate arecommended service for use in handling the application data payload 350and/or the most-recent application data item as may correspond to theextracted application data item 355. In some embodiments, theapplication service recommendation package may be received as part ofthe message package 170, such that receiving an application servicerecommendation package comprises received the message package 170 andextracting the application service recommendation package from themessage package 170.

The application interoperation component 160 may display a servicerecommendation on a display device for the recipient client device 120,the service recommendation corresponding to the application serviceidentifier. The service recommendation may comprise one of theapplications displayed for launching as described with reference to theapplication selection controls 240 of FIG. 2B. The applicationinteroperation component 160 may receive a user command, the usercommand indicating selection of the service recommendation.

In some embodiments, an application service recommendation package maycomprise a plurality of application service identifiers including theapplication service identifier, wherein each of the application serviceidentifiers embodies a recommendation of a particular applicationservice. For example, multiple transportation applications may berecommended, as in the illustrated embodiment of FIG. 2B. In some cases,a plurality of recommendations may be divided into categories. Theapplication interoperation component 160 may display a plurality ofservice recommendations on the display device for the client device, theplurality of service recommendations corresponding to the plurality ofapplication service identifiers and receive a user commend, the usercommand indicating selection of the service recommendation correspondingto the recommended application service.

A application service recommendation or a plurality of applicationservice recommendations may be specified by the messaging service 180based on the application data payload 350, and may be specified inparticular based on the extracted application data item 355. Theselection of one or more service recommendations by the messaging server180 may be performed in response to a type or types of informationrecorded in the application data payload 350 and/or the extractedapplication data item 355. Various application services may beassociated by the messaging system with particular types ofinformation—such as address information, time information, mediakeywords, etc.—and the application services selected based on theirassociated type or types of information matching the type or types ofinformation stored in the application data payload 350 and/or extractedapplication data item 355. The particular matching application servicesrecommended may further be selected and/or ranked based on a history ofthe user of the recipient client device 120, such as may indicatepreferences for particular applications through previous use of theparticular applications.

For instance, the application data payload 350 may comprise at leasttime information and location information, with the recommendedapplication service comprising a transportation application service. Theapplication service recommendation package comprising a transportationapplication service recommendation may therefore be based on theapplication data payload 350 comprising the time information and thelocation information. Similarly, the message package 170 may comprise amedia item, with the application data payload 350 comprising keywordinformation for the media item. The recommended application service maytherefore be a media application service, such that transmitting theapplication data payload to the media application service configures themedia application service for the retrieval of a plurality of mediaitems based on the keyword information. In another instance, theapplication data payload 350 may comprise gameplay information for agame application, the recommended application service comprising thegame application. The gameplay information may be operative to configurethe game application as to participation by the sender messaging accountin gameplay of the game application.

In some cases, particularly for the sharing of media items, the sameapplication service may be recommended as generated the extractedapplication data item 355. As such, the portion of the application datapayload 350 transmitted to a recommended application service may havebeen generated by the recommended application service operating for thesource messaging account.

The application interoperation component 160 may transmit at least aportion of the application data payload 350, such as the extractedapplication data item 355, to a recommended application service, therecommended application service identified by the application serviceidentifier. The application data payload 350 may be operative toconfigure the recommended application service as to context of amessaging conversation between the source messaging account and therecipient messaging account. In some cases, transmitting the applicationdata payload 350 or the portion of the application data payload 350 tothe recommended application service may comprise performing aninter-application transmission internal to the recipient client device120, the inter-application transmission transmitted to alocally-executing application 330. In other cases, transmitting theapplication data payload 350 or the portion of the application datapayload 350 to the recommended application service may compriseperforming a network transmission to an application server 335 for therecommended application service.

In some embodiments, application data may be passed with an identifierfor one or more of the participants in a messaging conversation. In someembodiments, the identifier may be a global identifier for the user withthe messaging system. In another embodiment, the identifier may be anapplication-scoped identifier specific to the application service towhich the application-scoped identifier is passed, theapplication-scoped identifier traceable back to the global identifier bythe messaging system but not by the application service, so as toprotect the privacy of the user of the messaging service 180. A numberof the identifiers may be used by the application service to configureservice, such as a transportation service knowing how many people are tobe transported based on the number of identifiers received. The numberof identifiers may be arbitrarily large, such as in a groupconversation.

FIG. 4 illustrates an embodiment of an additional application data item455 being added to an application data payload 350 to generate anupdated application data payload 450.

An application data item may be received from an application service. Insome cases, the application data item may comprise an additionalapplication data item 455 received from a recommended applicationservice in response to transmitting at least the portion of theapplication data payload 350 to the recommended application service. Asillustrated in FIG. 4, in some cases an additional application data item455 may be received from a locally-executing application on the samerecipient client device 120 via inter-application communication, and inother cases the additional application data item 455 may be receivedfrom the application server 355 without a local installation of anapplication 330 acting as an intermediary. The messaging component 150may transmit a second message package 470 to the messaging service, thesecond message package 470 including the additional application dataitem 455 in an updated application data payload 450.

In some embodiments, an application data payload may comprise only themost recent application data item received from an application service.In other embodiments, the application data payload may include a chainof application data items. Where a chain of application data items issupported, more than one application data item may be included in theapplication data payload where an additional application data item 455is temporally related and/or information-type related to one or moreapplication data items in the existing application data payload 350.

When an additional application data item 455 is received, theapplication interoperation component 160 may determine whether theexisting application data item or application data items in the existingapplication data payload 350 are temporally related to the additionalapplication data item 455, such as by determining whether the time ofthe reception of the additional application data item 455 issufficiently close to the time of the reception of the existingapplication data item(s) to indicate that they are related, as may bedetermined by through a threshold amount of time or other technique.Similarly, when an additional application data item 455 is received, theapplication interoperation component 160 may determine whether theexisting application data item(s) in the existing application datapayload 350 are information-type related to the additional applicationdata item 455, such as by determining whether they correspond to thesame type of information: time information, location information, timeand location information, event information, reservation information,media keyword information, etc.

The application interoperation component 160 may include the existingapplication data item(s) in an updated application data payload 450where the additional application data item 455 is temporally-related, isinformation-type related, or is both temporally-related andinformation-type related depending on the embodiment. In otherembodiments, the updated application data payload 450 transmitted by themessaging client 140 may always only comprise the additional applicationdata item 455, with the messaging server 180 determining whether toinclude the existing application data item(s) for transmission to thereceiving client device—the original sender client device 190 in theillustrated embodiment of FIG. 4—based on a similar analysis asdescribed with reference to the application interoperation component160, with the messaging server 180 including cached copies of theexisting application data item(s) in the updated application datapayload 450 when it is determined to do so.

As such, in some embodiments, the application data payload may grow withadded additional application data items so long as the additionalapplication data items being added remain temporally andinformation-type relevant to the chain of application data items in theapplication data payload. The application data payload may be reduced toonly a single application data item if the chain is broken eithertemporally or in regards to information-type. In these embodiments, theentire application data payload may always be passed to the receivingapplication service as any non-relevant application data items would beexcluded from the application data payload. As such, a transportationservice may receive a chain of location and/or time information, as mayrepresent the location of multiple destinations and/or users, therebyempowering the transportation service to go between multipledestinations and/or pick-up and drop-off multiple users. Similarly, amedia service may receive a chain of keywords and configure its searchof media content based on the chain of keywords, thereby incorporatingthe keywords for a chain of media being shared between users of amessaging system.

Included herein is a set of flow charts representative of exemplarymethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein, for example, in the form of a flowchart or flow diagram, are shown and described as a series of acts, itis to be understood and appreciated that the methodologies are notlimited by the order of acts, as some acts may, in accordance therewith,occur in a different order and/or concurrently with other acts from thatshown and described herein. For example, those skilled in the art willunderstand and appreciate that a methodology could alternatively berepresented as a series of interrelated states or events, such as in astate diagram. Moreover, not all acts illustrated in a methodology maybe required for a novel implementation.

FIG. 5 illustrates one embodiment of a logic flow 500. The logic flow500 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 5, the logic flow 500 mayreceive a message package from a messaging service at a messaging clienton a client device, the message package addressed from a sourcemessaging account and addressed to a recipient messaging account, therecipient messaging account associated with the messaging client on theclient device at block 502.

The logic flow 500 may extract an application data payload from themessage package at block 504.

The logic flow 500 may receive an application service recommendationpackage from the messaging service, the application servicerecommendation package comprising an application service identifier atblock 506.

The logic flow 500 may transmit at least a portion of the applicationdata payload to a recommended application service by the messagingclient, the recommended application service identified by theapplication service identifier at block 508.

The embodiments are not limited to this example.

FIG. 6 illustrates a block diagram of a centralized system 600. Thecentralized system 600 may implement some or all of the structure and/oroperations for the application data messaging system 100 in a singlecomputing entity, such as entirely within a single messaging serverdevice 620.

The messaging server device 620 may comprise any electronic devicecapable of receiving, processing, and sending information for theapplication data messaging system 100. Examples of an electronic devicemay include without limitation an ultra-mobile device, a mobile device,a personal digital assistant (PDA), a mobile computing device, a smartphone, a telephone, a digital telephone, a cellular telephone, ebookreaders, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, television, digitaltelevision, set top box, wireless access point, base station, subscriberstation, mobile subscriber center, radio network controller, router,hub, gateway, bridge, switch, machine, or combination thereof. Theembodiments are not limited in this context.

The messaging server device 620 may execute processing operations orlogic for the application data messaging system 100 using a processingcomponent 630. The processing component 630 may comprise varioushardware elements, software elements, or a combination of both. Examplesof hardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

The messaging server device 620 may execute communications operations orlogic for the application data messaging system 100 using communicationscomponent 640. The communications component 640 may implement anywell-known communications techniques and protocols, such as techniquessuitable for use with packet-switched networks (e.g., public networkssuch as the Internet, private networks such as an enterprise intranet,and so forth), circuit-switched networks (e.g., the public switchedtelephone network), or a combination of packet-switched networks andcircuit-switched networks (with suitable gateways and translators). Thecommunications component 640 may include various types of standardcommunication elements, such as one or more communications interfaces,network interfaces, network interface cards (NIC), radios, wirelesstransmitters/receivers (transceivers), wired and/or wirelesscommunication media, physical connectors, and so forth. By way ofexample, and not limitation, communication media 612 includes wiredcommunications media and wireless communications media. Examples ofwired communications media may include a wire, cable, metal leads,printed circuit boards (PCB), backplanes, switch fabrics, semiconductormaterial, twisted-pair wire, co-axial cable, fiber optics, a propagatedsignal, and so forth. Examples of wireless communications media mayinclude acoustic, radio-frequency (RF) spectrum, infrared and otherwireless media.

The messaging server device 620 may communicate with other devices 610,650 over a communications media 612 using communications signals 614 viathe communications component 640. The devices 610, 650 may be internalor external to the messaging server device 620 as desired for a givenimplementation.

The centralized system 600 may correspond to an embodiment in which asingle messaging server 180 is used executing on a single messagingserver device 620. The devices 610, 650 may correspond to clientdevices—such as recipient client device 120 and sender client device190—using the messaging server 180 for messaging services.

FIG. 7 illustrates a block diagram of a distributed system 700. Thedistributed system 700 may distribute portions of the structure and/oroperations for the application data messaging system 100 across multiplecomputing entities. Examples of distributed system 700 may includewithout limitation a client-server architecture, a 3-tier architecture,an N-tier architecture, a tightly-coupled or clustered architecture, apeer-to-peer architecture, a master-slave architecture, a shareddatabase architecture, and other types of distributed systems. Theembodiments are not limited in this context.

The distributed system 700 may comprise a messaging server device 710and an application server device 750. In general, the server devices710, 750 may be the same or similar to the centralized messaging serverdevice 620 as described with reference to FIG. 6. For instance, theserver devices 710, 750 may each comprise a processing component 730 anda communications component 740 which are the same or similar to theprocessing component 630 and the communications component 640,respectively, as described with reference to FIG. 6. In another example,the server devices 710, 750 may communicate over a communications media712 using communications signals 714 via the communications components740.

The plurality of messaging server devices 710 may comprise or employ oneor more client programs that operate to perform various methodologies inaccordance with the described embodiments. In one embodiment, forexample, the plurality of messaging server devices 710 may collectivelyimplement the messaging server 180 as a distributed messaging server180. Each of the messaging server devices 710 may execute a messagingserver 180 to collectively provide messaging services to the users ofthe media messaging system 100.

The plurality of application server devices 750 may comprise or employone or more server programs that operate to perform variousmethodologies in accordance with the described embodiments. In oneembodiment, for example, the plurality of application server devices 750may implement the application servers 135.

FIG. 8 illustrates an embodiment of an exemplary computing architecture800 suitable for implementing various embodiments as previouslydescribed. In one embodiment, the computing architecture 800 maycomprise or be implemented as part of an electronic device. Examples ofan electronic device may include those described with reference to FIG.6 and FIG. 7, among others. The embodiments are not limited in thiscontext.

As used in this application, the terms “system” and “component” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution, examples of which are provided by the exemplary computingarchitecture 800. For example, a component can be, but is not limited tobeing, a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical and/or magnetic storage medium), anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution, and a component canbe localized on one computer and/or distributed between two or morecomputers. Further, components may be communicatively coupled to eachother by various types of communications media to coordinate operations.The coordination may involve the uni-directional or bi-directionalexchange of information. For instance, the components may communicateinformation in the form of signals communicated over the communicationsmedia. The information can be implemented as signals allocated tovarious signal lines. In such allocations, each message is a signal.Further embodiments, however, may alternatively employ data messages.Such data messages may be sent across various connections. Exemplaryconnections include parallel interfaces, serial interfaces, and businterfaces.

The computing architecture 800 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The embodiments, however, are not limited to implementation by thecomputing architecture 800.

As shown in FIG. 8, the computing architecture 800 comprises aprocessing unit 804, a system memory 806 and a system bus 808. Theprocessing unit 804 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium®, Pentium®,Xeon®, and XScale® processors; and similar processors. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as the processing unit 804.

The system bus 808 provides an interface for system componentsincluding, but not limited to, the system memory 806 to the processingunit 804. The system bus 808 can be any of several types of busstructure that may further interconnect to a memory bus (with or withouta memory controller), a peripheral bus, and a local bus using any of avariety of commercially available bus architectures. Interface adaptersmay connect to the system bus 808 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The computing architecture 800 may comprise or implement variousarticles of manufacture. An article of manufacture may comprise acomputer-readable storage medium to store logic. Examples of acomputer-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples oflogic may include executable computer program instructions implementedusing any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. Embodiments may also beat least partly implemented as instructions contained in or on anon-transitory computer-readable medium, which may be read and executedby one or more processors to enable performance of the operationsdescribed herein.

The system memory 806 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information. In the illustratedembodiment shown in FIG. 8, the system memory 806 can includenon-volatile memory 810 and/or volatile memory 812. A basic input/outputsystem (BIOS) can be stored in the non-volatile memory 810.

The computer 802 may include various types of computer-readable storagemedia in the form of one or more lower speed memory units, including aninternal (or external) hard disk drive (HDD) 814, a magnetic floppy diskdrive (FDD) 816 to read from or write to a removable magnetic disk 818,and an optical disk drive 820 to read from or write to a removableoptical disk 822 (e.g., a CD-ROM or DVD). The HDD 814, FDD 816 andoptical disk drive 820 can be connected to the system bus 808 by a HDDinterface 824, an FDD interface 826 and an optical drive interface 828,respectively. The HDD interface 824 for external drive implementationscan include at least one or both of Universal Serial Bus (USB) and IEEE1394 interface technologies.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 810, 812, including anoperating system 830, one or more application programs 832, otherprogram modules 834, and program data 836. In one embodiment, the one ormore application programs 832, other program modules 834, and programdata 836 can include, for example, the various applications and/orcomponents of the application data messaging system 100.

A user can enter commands and information into the computer 802 throughone or more wire/wireless input devices, for example, a keyboard 838 anda pointing device, such as a mouse 840. Other input devices may includemicrophones, infra-red (IR) remote controls, radio-frequency (RF) remotecontrols, game pads, stylus pens, card readers, dongles, finger printreaders, gloves, graphics tablets, joysticks, keyboards, retina readers,touch screens (e.g., capacitive, resistive, etc.), trackballs,trackpads, sensors, styluses, and the like. These and other inputdevices are often connected to the processing unit 804 through an inputdevice interface 842 that is coupled to the system bus 808, but can beconnected by other interfaces such as a parallel port, IEEE 1394 serialport, a game port, a USB port, an IR interface, and so forth.

A monitor 844 or other type of display device is also connected to thesystem bus 808 via an interface, such as a video adaptor 846. Themonitor 844 may be internal or external to the computer 802. In additionto the monitor 844, a computer typically includes other peripheraloutput devices, such as speakers, printers, and so forth.

The computer 802 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 848. The remote computer 848can be a workstation, a server computer, a router, a personal computer,portable computer, microprocessor-based entertainment appliance, a peerdevice or other common network node, and typically includes many or allof the elements described relative to the computer 802, although, forpurposes of brevity, only a memory/storage device 850 is illustrated.The logical connections depicted include wire/wireless connectivity to alocal area network (LAN) 852 and/or larger networks, for example, a widearea network (WAN) 854. Such LAN and WAN networking environments arecommonplace in offices and companies, and facilitate enterprise-widecomputer networks, such as intranets, all of which may connect to aglobal communications network, for example, the Internet.

When used in a LAN networking environment, the computer 802 is connectedto the LAN 852 through a wire and/or wireless communication networkinterface or adaptor 856. The adaptor 856 can facilitate wire and/orwireless communications to the LAN 852, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 856.

When used in a WAN networking environment, the computer 802 can includea modem 858, or is connected to a communications server on the WAN 854,or has other means for establishing communications over the WAN 854,such as by way of the Internet. The modem 858, which can be internal orexternal and a wire and/or wireless device, connects to the system bus808 via the input device interface 842. In a networked environment,program modules depicted relative to the computer 802, or portionsthereof, can be stored in the remote memory/storage device 850. It willbe appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computerscan be used.

The computer 802 is operable to communicate with wire and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.8 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.8x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

FIG. 9 illustrates a block diagram of an exemplary communicationsarchitecture 900 suitable for implementing various embodiments aspreviously described. The communications architecture 900 includesvarious common communications elements, such as a transmitter, receiver,transceiver, radio, network interface, baseband processor, antenna,amplifiers, filters, power supplies, and so forth. The embodiments,however, are not limited to implementation by the communicationsarchitecture 900.

As shown in FIG. 9, the communications architecture 900 comprisesincludes one or more clients 902 and servers 904. The clients 902 mayimplement the first server device 910. The servers 904 may implement thesecond server device 950. The clients 902 and the servers 904 areoperatively connected to one or more respective client data stores 908and server data stores 910 that can be employed to store informationlocal to the respective clients 902 and servers 904, such as cookiesand/or associated contextual information.

The clients 902 and the servers 904 may communicate information betweeneach other using a communication framework 906. The communicationsframework 906 may implement any well-known communications techniques andprotocols. The communications framework 906 may be implemented as apacket-switched network (e.g., public networks such as the Internet,private networks such as an enterprise intranet, and so forth), acircuit-switched network (e.g., the public switched telephone network),or a combination of a packet-switched network and a circuit-switchednetwork (with suitable gateways and translators).

The communications framework 906 may implement various networkinterfaces arranged to accept, communicate, and connect to acommunications network. A network interface may be regarded as aspecialized form of an input output interface. Network interfaces mayemploy connection protocols including without limitation direct connect,Ethernet (e.g., thick, thin, twisted pair 10/100/1000 Base T, and thelike), token ring, wireless network interfaces, cellular networkinterfaces, IEEE 802.11a-x network interfaces, IEEE 802.16 networkinterfaces, IEEE 802.20 network interfaces, and the like. Further,multiple network interfaces may be used to engage with variouscommunications network types. For example, multiple network interfacesmay be employed to allow for the communication over broadcast,multicast, and unicast networks. Should processing requirements dictatea greater amount speed and capacity, distributed network controllerarchitectures may similarly be employed to pool, load balance, andotherwise increase the communicative bandwidth required by clients 902and the servers 904. A communications network may be any one and thecombination of wired and/or wireless networks including withoutlimitation a direct interconnection, a secured custom connection, aprivate network (e.g., an enterprise intranet), a public network (e.g.,the Internet), a Personal Area Network (PAN), a Local Area Network(LAN), a Metropolitan Area Network (MAN), an Operating Missions as Nodeson the Internet (OMNI), a Wide Area Network (WAN), a wireless network, acellular network, and other communications networks.

FIG. 10 illustrates an embodiment of a device 1000 for use in amulticarrier OFDM system, such as the application data messaging system100. Device 1000 may implement, for example, software components 1060 asdescribed with reference to application data messaging system 100 and/ora logic circuit 1035. The logic circuit 1035 may include physicalcircuits to perform operations described for the application datamessaging system 100. As shown in FIG. 10, device 1000 may include aradio interface 1010, baseband circuitry 1020, and computing platform1030, although embodiments are not limited to this configuration.

The device 1000 may implement some or all of the structure and/oroperations for the application data messaging system 100 and/or logiccircuit 1035 in a single computing entity, such as entirely within asingle device. Alternatively, the device 1000 may distribute portions ofthe structure and/or operations for the application data messagingsystem 100 and/or logic circuit 1035 across multiple computing entitiesusing a distributed system architecture, such as a client-serverarchitecture, a 3-tier architecture, an N-tier architecture, atightly-coupled or clustered architecture, a peer-to-peer architecture,a master-slave architecture, a shared database architecture, and othertypes of distributed systems. The embodiments are not limited in thiscontext.

In one embodiment, radio interface 1010 may include a component orcombination of components adapted for transmitting and/or receivingsingle carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK) and/or orthogonal frequency divisionmultiplexing (OFDM) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. Radiointerface 1010 may include, for example, a receiver 1012, a transmitter1016 and/or a frequency synthesizer 1014. Radio interface 1010 mayinclude bias controls, a crystal oscillator and/or one or more antennas1018. In another embodiment, radio interface 1010 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 1020 may communicate with radio interface 1010 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 1022 for down converting received signals, adigital-to-analog converter 1024 for up converting signals fortransmission. Further, baseband circuitry 1020 may include a baseband orphysical layer (PHY) processing circuit 1056 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry1020 may include, for example, a processing circuit 1028 for mediumaccess control (MAC)/data link layer processing. Baseband circuitry 1020may include a memory controller 1032 for communicating with processingcircuit 1028 and/or a computing platform 1030, for example, via one ormore interfaces 1034.

In some embodiments, PHY processing circuit 1026 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames, such as radio frames. Alternatively or inaddition, MAC processing circuit 1028 may share processing for certainof these functions or perform these processes independent of PHYprocessing circuit 1026. In some embodiments, MAC and PHY processing maybe integrated into a single circuit.

The computing platform 1030 may provide computing functionality for thedevice 1000. As shown, the computing platform 1030 may include aprocessing component 1040. In addition to, or alternatively of, thebaseband circuitry 1020, the device 1000 may execute processingoperations or logic for the application data messaging system 100 andlogic circuit 1035 using the processing component 1040. The processingcomponent 1040 (and/or PHY 1026 and/or MAC 1028) may comprise varioushardware elements, software elements, or a combination of both. Examplesof hardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

The computing platform 1030 may further include other platformcomponents 1050. Other platform components 1050 include common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components (e.g., digital displays), powersupplies, and so forth. Examples of memory units may include withoutlimitation various types of computer readable and machine readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Device 1000 may be, for example, an ultra-mobile device, a mobiledevice, a fixed device, a machine-to-machine (M2M) device, a personaldigital assistant (PDA), a mobile computing device, a smart phone, atelephone, a digital telephone, a cellular telephone, user equipment,eBook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, television, digitaltelevision, set top box, wireless access point, base station, node B,evolved node B (eNB), subscriber station, mobile subscriber center,radio network controller, router, hub, gateway, bridge, switch, machine,or combination thereof. Accordingly, functions and/or specificconfigurations of device 1000 described herein, may be included oromitted in various embodiments of device 1000, as suitably desired. Insome embodiments, device 1000 may be configured to be compatible withprotocols and frequencies associated one or more of the 3GPP LTESpecifications and/or IEEE 1002.16 Standards for WMANs, and/or otherbroadband wireless networks, cited herein, although the embodiments arenot limited in this respect.

Embodiments of device 1000 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1018) for transmission and/orreception using adaptive antenna techniques for beamforming or spatialdivision multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of device 1000 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 1000 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 1000 shown in theblock diagram of FIG. 10 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

A computer-implemented method may comprise receiving a message packagefrom a messaging service at a messaging client on a client device, themessage package addressed from a source messaging account and addressedto a recipient messaging account, the recipient messaging accountassociated with the messaging client on the client device; extracting anapplication data payload from the message package; receiving anapplication service recommendation package from the messaging service,the application service recommendation package comprising an applicationservice identifier; and transmitting at least a portion of theapplication data payload to a recommended application service by themessaging client, the recommended application service identified by theapplication service identifier.

A computer-implemented method may further comprise displaying a servicerecommendation on a display device for the client device, the servicerecommendation corresponding to the application service identifier; andreceiving a user command, the user command indicating selection of theservice recommendation.

A computer-implemented method may further comprise the applicationservice recommendation package comprising a plurality of applicationservice identifiers including the application service identifier,further comprising: displaying a plurality of service recommendations onthe display device for the client device, the plurality of servicerecommendations corresponding to the plurality of application serviceidentifiers; and receiving a user commend, the user command indicatingselection of the service recommendation corresponding to the recommendedapplication service.

A computer-implemented method may further comprise the application datapayload operative to configure the recommended application service as tocontext of a messaging conversation between the source messaging accountand the recipient messaging account.

A computer-implemented method may further comprise the portion of theapplication data payload generated by the recommended applicationservice for the source messaging account.

A computer-implemented method may further comprise the applicationservice recommendation specified by the messaging service based on theapplication data payload.

A computer-implemented method may further comprise the application datapayload comprising at least one of time information, locationinformation, and event information.

A computer-implemented method may further comprise the application datapayload comprising at least time information and location information,the recommended application service comprising a transportationapplication service, the application service recommendation packagecomprising a transportation application service recommendation based onthe application data payload comprising the time information and thelocation information.

A computer-implemented method may further comprise the message packagecomprising a media item, the application data payload comprising keywordinformation for the media item, the recommended application servicecomprising a media application service, wherein transmitting theapplication data payload to the media application service configures themedia application service for the retrieval of a plurality of mediaitems based on the keyword information.

A computer-implemented method may further comprise the application datapayload comprising gameplay information for a game application, therecommended application service comprising the game application, thegameplay information operative to configure the game application as toparticipation by the sender messaging account in gameplay of the gameapplication.

A computer-implemented method may further comprise receiving anapplication data item from the recommended application service inresponse to transmitting at least the portion of the application datapayload to the recommended application service; and transmitting asecond message package to the messaging service, the second messagepackage including the application data item in an updated applicationdata payload.

An apparatus may comprise a processor circuit on a client device; anetwork interface controller on a client device; a messaging componentoperative on the processor circuit to receive a message package from amessaging service at a messaging client on a client device via thenetwork interface controller, the message package addressed from asource messaging account and addressed to a recipient messaging account,the recipient messaging account associated with the messaging client onthe client device; extract an application data payload from the messagepackage; receive an application service recommendation package from themessaging service, the application service recommendation packagecomprising an application service identifier; and an applicationinteroperation component operative on the processor circuit to transmitat least a portion of the application data payload to a recommendedapplication service by the messaging client, the recommended applicationservice identified by the application service identifier. The apparatusmay be operative to implement any of the computer-implemented methodsdescribed herein.

At least one computer-readable storage medium may comprise instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Further, some embodiments may be described using the expression“coupled” and “connected” along with their derivatives. These terms arenot necessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein which form part of one or more embodiments.Rather, the operations are machine operations. Useful machines forperforming operations of various embodiments include general purposedigital computers or similar devices.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose or it may comprise a general purpose computer asselectively activated or reconfigured by a computer program stored inthe computer. The procedures presented herein are not inherently relatedto a particular computer or other apparatus. Various general purposemachines may be used with programs written in accordance with theteachings herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. The requiredstructure for a variety of these machines will appear from thedescription given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thusthe following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

1. A computer-implemented method, comprising: receiving a messagepackage addressed to a recipient messaging account, the message packageincluding an application data payload; transmitting, to one or moremessaging endpoints associated with the recipient messaging account, themessage package and an application service recommendation package;wherein the application service recommendation package includes one ormore application service identifiers identifying one or more applicationservices for handling the application data payload.
 2. Thecomputer-implemented method of claim 1 wherein the application servicerecommendation package is included in the message package.
 3. Thecomputer-implemented method of claim 1 further comprising: selecting oneor more application service identifiers for inclusion in the applicationservice recommendation package, the one or more application serviceidentifiers are selected based on the type of information contained inthe application data payload.
 4. The computer-implemented method ofclaim 1 further comprising: selecting one or more application serviceidentifiers for inclusion in the application service recommendationpackage, the one or more application service identifiers are selectedbased on a history of a user associated with the recipient messagingaccount, the history indicating user preferences for particularapplications based upon previous use of the particular application bythe user.
 5. The computer-implemented method of claim 4 wherein the oneor more application service identifiers are ranked based on the history.6. The computer-implemented method of claim 1 further comprising:queuing the message package in a recipient message queue associated withthe recipient messaging account for delivery to the one or moremessaging endpoints.
 7. The computer-implemented method of claim 1wherein the application data payload includes a hash associated with amedia element, further comprising: determining that the media element isnot stored in a local cache or in a media server; uploading the mediaelement into the local cache or media server; and including the hash orthe media element in the application data payload transmitted to themessaging endpoints associated with the recipient messaging account. 8.The computer-implemented method of claim 1 wherein the application datapayload includes a hash associated with a media element, furthercomprising: determining that the media element is stored in a localcache or in a media server; retrieving the media element; and includingthe media element in the application data payload transmitted to themessaging endpoints associated with the recipient messaging account. 9.An apparatus, comprising: a processor circuit on a server device; anetwork interface controller on a server device; a messaging serveroperative on the processor circuit to: receive, via the networkinterface controller, a message package addressed to a recipientmessaging account, the message package including an application datapayload; generate an application service recommendation packagecomprising one or more application service identifiers identifying oneor more application services for handling the application data payload;and transmit, via the network interface controller, to one or moremessaging endpoints associated with the recipient messaging account, themessage package and the application service recommendation package. 10.The apparatus of claim 9 wherein the messaging server is furtheroperative to: select one or more application service identifiers forinclusion in the application service recommendation package, the one ormore application service identifiers being selected based on the type ofinformation contained in the application data payload.
 11. The apparatusof claim 9 where in the messaging server is further operative to: selectone or more application service identifiers for inclusion in theapplication service recommendation package, the one or more applicationservice identifiers being selected based on a history of a userassociated with the recipient messaging account, the history indicatinguser preferences for particular applications based upon previous use ofthe particular application by the user.
 12. The apparatus of claim 9further wherein the messaging server is further operative to: queue themessage package in a recipient message queue associated with therecipient messaging account for delivery to the one or more messagingendpoints.
 13. The apparatus of claim 9 wherein the application datapayload includes a hash associated with a media element, the messagingserver further operative to: determine that the media element is notstored in a local cache or in a media server; upload the media elementinto the local cache or media server; and include the hash or the mediaelement in the application data payload transmitted to the messagingendpoints associated with the recipient messaging account.
 14. Theapparatus of claim 9 wherein the application data payload includes ahash associated with a media element, the messaging server furtheroperative to: determine that the media element is stored in a localcache or in a media server; retrieve the media element; and include themedia element in the application data payload transmitted to themessaging endpoints associated with the recipient messaging account. 15.A non-transitory computer-readable storage medium comprisinginstructions that, when executed, cause a system to: receive a messagepackage addressed to a recipient messaging account, the message packageincluding an application data payload; generate an application servicerecommendation package comprising one or more application serviceidentifiers identifying one or more application services for handlingthe application data payload; and transmit, via the network interfacecontroller, to one or more messaging endpoints associated with therecipient messaging account, the message package and the applicationservice recommendation package.
 16. The computer-readable storage mediumof claim 15 comprising further instructions that, when executed, cause asystem to: select one or more application service identifiers forinclusion in the application service recommendation package, the one ormore application service identifiers are selected based on the type ofinformation contained in the application data payload.
 17. Thecomputer-readable storage medium of claim 15 comprising furtherinstructions that, when executed, cause a system to: select one or moreapplication service identifiers for inclusion in the application servicerecommendation package, the one or more application service identifiersare selected based on a history of a user associated with the recipientmessaging account, the history indicating user preferences forparticular applications based upon previous use of the particularapplication by the user.
 18. The computer-readable storage medium ofclaim 15 comprising further instructions that, when executed, cause asystem to: queue the message package in a recipient message queueassociated with the recipient messaging account for delivery to the oneor more messaging endpoints.
 19. The computer-readable storage medium ofclaim 15 wherein the application data payload includes a hash associatedwith a media element, comprising further instructions that, whenexecuted, cause a system to: determine that the media element is notstored in a local cache or in a media server; upload the media elementinto the local cache or media server; and include the hash or the mediaelement in the application data payload transmitted to the messagingendpoints associated with the recipient messaging account.
 20. Thecomputer-readable storage medium of claim 15 wherein the applicationdata payload includes a hash associated with a media element, comprisingfurther instructions that, when executed, cause a system to: determinethat the media element is stored in a local cache or in a media server;retrieve the media element; and include the media element in theapplication data payload transmitted to the messaging endpointsassociated with the recipient messaging account.